Hi, Thanks for your post. In order to troubleshoot, please apply the latest update for the NIC driver. You may also temporarily disable TCP Offloading, RSS and TCP Chimney, to see if the issue still persists. You can run the following command line to disable it. netsh int tcp set global chimney=disabled netsh int tcp set global rss=disabled netsh int ip set global taskoffload=disabled netsh int tcp set global autotuninglevel=disabled netsh int tcp set global congestionprovider=none netsh int tcp set global ecncapability=disabled netsh int tcp set global timestamps=disabled Information about the TCP Chimney Offload, Receive Side Scaling, and Network Direct Memory Access features in Windows Server 2008 http://support.microsoft.com/kb/951037 How to Troubleshoot Basic TCP/IP Problems http://support.microsoft.com/default.aspx?scid=kb;EN-US;169790 Best Regards, Aiden TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.Aiden Cao TechNet Community Support

I've got a strange issue on my 2008 R2 SP1 web server: immediately after reboot, the network "identifying" procedure will not complete. This machine can sit "identifying" for several *days*. During this, I can access its file shares and the main IIS website. But cannot log on thru RDP, neither access a Tomcat webserver. If I log on on the glass console and disable/enable the LAN adapter, the "identification" succeedes very quickly and everything is well - until the server restarts again (usually because of instaling updates). This machine has a Realtek RTL8168D netcard (yep, not quite a server grade) and VMware player's virtual interfaces (idle, no VMs running). Only IPv4 is enabled on the LAN. both IPv6 and ip4 enabled on VMware adapters. Why it behaves this way? Are there any cures? Thanks for any idea, -- pa